You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a problem caused by your code, or is it specifically because of the library?
I have double-checked my code carefully.
Describe the bug.
When WhatsApp Web sends a call_log update, the raw payload often does not include the isNewMsgfield. Because whatsapp-web.js currently does:
if(msg.isNewMsg){
...
}
node_modules/whatsapp-web.js/src/Client.js:701
all call_log messages are silently ignored and never emitted as high-level message events.
Expected Behavior
call_log messages should be emitted when received, even if isNewMsg is undefined. Call-log notifications (missed or received calls) are legitimate “new” events and should not be filtered out.
Steps to Reproduce the Bug or Issue
Use LocalAuth (or your chosen auth strategy) and instantiate a Client.
Place or miss a call to the WhatsApp number—this generates a call_log update.
Observe in your debugger that the raw event payload has type === 'call_log'but noisNewMsg property.
Notice your message listener is never called for call logs.
WhatsApp Account Type
Standard
Browser Type
Chromium
Operation System Type
Linux
Phone OS Type
Android
WhatsApp-Web.js Version
v1.28.0
WhatsApp Web Version
2.3000.1023186384
Node.js Version
20.18.1
Authentication Strategy
LocalAuth
Additional Context
Call logs are functionally "new messages" (notifications), so the isNewMsg check is overly strict. A fix could:
Default isNewMsg to true for call_log types, or
Skip the check entirely for call logs.
The text was updated successfully, but these errors were encountered:
I have updated the node version. It didn't help. The problem lies precisely in the call_log message itself. Other messages have the isNewMsg field and arrive correctly.
Is there an existing issue for this?
Is this a problem caused by your code, or is it specifically because of the library?
Describe the bug.
When WhatsApp Web sends a
call_log
update, the raw payload often does not include theisNewMsg
field. Because whatsapp-web.js currently does:node_modules/whatsapp-web.js/src/Client.js:701
all
call_log
messages are silently ignored and never emitted as high-levelmessage
events.Expected Behavior
call_log
messages should be emitted when received, even ifisNewMsg
is undefined. Call-log notifications (missed or received calls) are legitimate “new” events and should not be filtered out.Steps to Reproduce the Bug or Issue
Client
.call_log
update.type === 'call_log'
but noisNewMsg
property.message
listener is never called for call logs.WhatsApp Account Type
Standard
Browser Type
Chromium
Operation System Type
Linux
Phone OS Type
Android
WhatsApp-Web.js Version
v1.28.0
WhatsApp Web Version
2.3000.1023186384
Node.js Version
20.18.1
Authentication Strategy
LocalAuth
Additional Context
Call logs are functionally "new messages" (notifications), so the isNewMsg check is overly strict. A fix could:
Default isNewMsg to true for call_log types, or
Skip the check entirely for call logs.
The text was updated successfully, but these errors were encountered: